Pseudo-random dynamic scheduler for scheduling communication periods between electronic devices

ABSTRACT

An electronic device is disclosed that is adapted to communicate with a first device network and to communicate with a second device that is part of a second device network. The device includes a processor and a communications module in electronic communication with the processor for communications with other devices including the second device and at least one device from the first device network. Memory may also be included in electronic communication with the processor for storing data. The electronic device may also include a pseudo-random scheduler for providing time points defining a schedule for the electronic device to communicate with the other devices. A dynamic scheduler may also be included to modify the schedule. The electronic device may also include an event queue.

RELATED APPLICATIONS

This application is related to and claims priority from U.S. PatentApplication Ser. No. 60/272,630 filed Feb. 28, 2001, for “Effectivescheduling of inter system communication,” with inventor Daryl Hlasny,which is incorporated herein by reference.

TECHNICAL FIELD

This invention relates generally to electronic devices, and is moreparticularly directed toward systems and methods for schedulingcommunication periods between electronic devices.

BACKGROUND

Computer and communication technologies continue to advance at a rapidpace. Indeed, computer and communication technologies are involved inmany aspects of a person's day. For example, many devices being usedtoday by consumers have a small computer incorporated within the device.These small computers come in varying sizes and degrees ofsophistication. These small computers may vary in sophistication fromone microcontroller to a fully-functional complete computer system. Forexample, small computers may be a one-chip computer, such as amicrocontroller, a one-board type of computer, such as a controller, atypical desktop computer, such as an IBM-PC compatible, etc.

Computers typically have one or more processors. The processor(s)usually are interconnected to different external inputs and outputs andfunction to manage the particular computer or device. For example, aprocessor in a thermostat may be connected to buttons used to select thetemperature setting, to the furnace or air conditioner to change thetemperature, and to temperature sensors to read and display the currenttemperature on a display.

Many appliances, devices, etc., include one or more small computers. Forexample, thermostats, furnaces, air conditioning systems, refrigerators,telephones, typewriters, automobiles, vending machines, and manydifferent types of industrial equipment now typically have smallcomputers, or processors, inside of them. Computer software runs theprocessors of these computers and tells the processors what to do tocarry out certain tasks. For example, the computer software running on athermostat may cause an air conditioner to stop running when aparticular temperature is reached or may cause a heater to turn on whenneeded.

These types of small computers that are a part of a device, appliance,tool, etc., are often referred to as embedded systems. The term“embedded system” usually refers to computer hardware and software thatis part of a larger system. Embedded systems may not have typical inputand output devices such as a keyboard, mouse, and/or monitor. Usually,at the heart of each embedded system is one or more processor(s).

With the increased use of electronic devices and embedded systems, andwith the increased demands for the exchange of information, more devicesare now able to detect surrounding devices and establish electroniccommunications with these devices. The Bluetooth specification definesone standard whereby devices can communicate with each other throughshort-range radio signals. Many kinds of devices may benefit from beingable to connect to other devices without needing user intervention. Forexample, printers, personal digital assistants, digital cameras,telephones, laptop computers, video monitors, electronic calendars,desktops, fax machines, keyboards, joysticks, etc., may all become partof a short-range radio system to connect to other devices. By enablingthis type of communication, a bridge is provided to existing datanetworks to form small private ad hoc groupings of connected devicesaway from fixed network infrastructures. Thus, device networks may beformed on-the-fly as devices discover each other. However, as moredevices attempt to communicate with one another, inefficiencies mayarise that may slow down or otherwise hinder the overall communicationof one or more electronic devices. Thus, benefits may be realized ifcommunications by electronic devices were enhanced with additionalsystems and methods for providing more effective communicationtechniques.

SUMMARY OF THE INVENTION

An electronic device is disclosed that is adapted to communicate with afirst device network and to communicate with a second device that ispart of a second device network. The device includes a processor and acommunications module in electronic communication with the processor forcommunications with other devices including the second device and atleast one device from the first device network. Memory may also beincluded in electronic communication with the processor for storingdata. The electronic device may also include a pseudo-random schedulerfor providing time points defining a schedule for the electronic deviceto communicate with the other devices. A dynamic scheduler may also beincluded to modify the schedule. The electronic device may also includean event queue.

The dynamic scheduler may implement a fair allocation method ofdynamically allocating communication bandwidth. The fair allocationmethod may include extending previous communications periods. The fairallocation method may also include reducing the number of initiationtime points in the event queue.

An opportunistic allocation method may be implemented by the dynamicscheduler to dynamically allocate communication bandwidth. Theopportunistic allocation method may include evaluating traffic pendingand device availability and modifying the schedule based on theevaluation.

The pseudo-random scheduler may implement a predetermined synchronizedmethod for generating time points. In addition, the pseudo-randomscheduler may implement a predetermined asynchronized method forgenerating time points. A real-time method may also be used in thepseudo-random scheduler.

The event queue may include a plurality of initiation time points. Aplurality of channel identifications may also be stored in the eventqueue. Further, the event queue may include a plurality of data pendingindicators.

The electronic device may further include a state machine for schedulingand communicating. The state machine may include an idle state, a datastate, a negotiate schedule state and a re-establish state.

The electronic device may be used in a Bluetooth system. In such anenvironment, the device may become part of a piconet. If the devicebecomes part of a piconet, the pseudo-random scheduler may provide timepoints defining the schedule for the electronic device to communicatewith piconets.

A method is also disclosed for pseudo-randomly and dynamicallyscheduling communication periods between electronic devices. The methodmay include the steps of transmitting outbound data from a firstelectronic device to a first device network and receiving inbound databy the first electronic device from the first device network. The methodmay also include the steps of discovering a second electronic device ofa second device network, providing pseudo-random time points defining aschedule for the first electronic device to communicate with the firstdevice network and with the second electronic device, storing the timepoints in an event queue, and dynamically modifying the schedule to addadditional communication bandwidth to at least one communicationchannel.

A computer-readable medium for carrying program data is also disclosed.The program data includes executable instructions for implementing amethod. The method may include the steps of transmitting outbound datafrom a first electronic device to a first device network and receivinginbound data by the first electronic device from the first devicenetwork. The method may also include the steps of discovering a secondelectronic device of a second device network, providing pseudo-randomtime points defining a schedule for the first electronic device tocommunicate with the first device network and with the second electronicdevice, storing the time points in an event queue, and dynamicallymodifying the schedule to add additional communication bandwidth to atleast one communication channel.

BRIEF DESCRIPTION OF THE DRAWINGS

The present embodiments will become more fully apparent from thefollowing description and appended claims, taken in conjunction with theaccompanying drawings. Understanding that these drawings depict onlytypical embodiments and are, therefore, not to be considered limiting ofthe invention's scope, the embodiments will be described with additionalspecificity and detail through use of the accompanying drawings inwhich:

FIG. 1A is a block diagram of an embodiment of a device pair;

FIG. 1B is a communication period diagram for an embodiment of a devicepair;

FIG. 1C is a communication period diagram for an embodiment of a devicepair illustrating a series of communication periods;

FIG. 2A is a block diagram of two device networks;

FIG. 2B is a block diagram of two device networks with an intersystemcommunication link between slave devices;

FIG. 2C is a block diagram of two device networks with an intersystemcommunication link between master devices;

FIG. 2D is a block diagram of two device networks with an intersystemcommunication link between a master and a slave;

FIG. 3A is a block diagram illustrating an embodiment of two devicepairs;

FIG. 3B is a communication period diagram for an embodiment of twodevice pairs;

FIG. 4 illustrates a device network topology generalization;

FIG. 5 is block diagram illustrating hardware components of anembodiment of an electronic device;

FIG. 6 is block diagram illustrating software components of anembodiment of an electronic device;

FIG. 7 is a state machine diagram illustrating an embodiment of a statemachine for the scheduler of a device;

FIG. 8A is a timing diagram illustrating a predetermined synchronizedmethod for generating time points;

FIG. 8B is a timing diagram illustrating a predetermined asynchronizedmethod for generating time points;

FIG. 8C is a timing diagram illustrating a real-time method forgenerating time points;

FIG. 9A is a block diagram of a device network including three masterdevices;

FIG. 9B is a communication period diagram for the embodiment of FIG. 9A;

FIG. 10A is a block diagram of a device network including three masterdevices, one slave device, and one master/slave device;

FIG. 10B is a communication period diagram for the embodiment of FIG.10A;

FIG. 11A is a block diagram of a device network including four devices;

FIG. 11B is a communication period diagram for the embodiment of FIG.11A;

FIG. 12A is a block diagram of a device network including five devices;and

FIG. 12B is a communication period diagram for the embodiment of FIG.12A.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments asgenerally described and illustrated in the Figures herein, could bearranged and designed in a wide variety of different configurations.Thus, the following more detailed description of the embodiments of thesystem and method of the present invention, as represented in theFigures, is not intended to limit the scope of the invention, asclaimed, but is merely representative of the embodiments of theinvention.

FIG. 1A is a block diagram illustrating two electronic devices 102, 104that comprise a device pair 106. The device pair 106 may enter intocommunication 108 with one another. Some examples of an electronicdevice 102, 104 are a vending machine, a telephone, a door lock, atemperature sensor, a motor, a switch, a light, a printer, a faxmachine, a refrigerator, a health monitor, an elevator/escalator, acopier, a scanner, manufacturing equipment, industrial equipmentscomputer equipment and peripherals, security systems, monitoringequipment, a thermostat, and the like.

FIG. 1B illustrates a communication period diagram that includes aschedule 110 for a communication period 112 between the two devices 102,104 of the device pair 106. Typically a schedule 110 is created for eachpair 106 of devices that wish to communicate. The schedule 110 may bespecific to the device pair 106 and may be known by both devices 102,104. As shown, the schedule 110 may include time points 114, 116 thatsignal the initiation and termination of the communication between thedevice pair 106. The time between the initiation time point 114 and thetermination event 116 is called the communication period 112.

An initiation time point 114 is the typical method used to startcommunication between two devices 102, 104. Both devices 102, 104 areusually aware of the initiation time point 114 so that they may startcommunication at this time.

In the embodiment of FIG. 1A, either device 102, 104 may terminatecommunication. A device may arbitrarily terminate the communicationperiod 112, but typically the period 112 is terminated by a conflictingtime point from another device pair schedule. Termination may beaccomplished by signaling between the device pair 106 on a perconnection basis. A termination time point 116 may be used to end thecommunication period 112 but is not essential. Termination time points116 are created by the schedule negotiation process that is carried outbetween pairs of devices.

Typically, initiation time points 114 are determined by a predeterminedpseudo random schedule that is unique and random relative to the pseudorandom schedule for other interconnected devices pairs. Initiation timepoints 114 may also be determined by a negotiation between each pair ofdevices where the negotiated time point is within a valid communicationperiod as determined by the predetermined pseudo random schedule. Thenegotiation process is performed between device pairs and is used tocreate free time in the schedule for other purposes.

A device pair 106 typically consists of one device that has the role ofmaster with respect to the connection and another device that has therole of slave. The master device typically initiates and controls theconnection, while the slave responds to the master's commands. Theschedule typically uses the time base of the clock of the master device.The slave device may maintain synchronization with this clock. Anothertime base may be used if available to both devices.

FIG. 1C is a communication period diagram illustrating a series ofcommunication periods 118, 120, 122 comprised of multiple initiationtime points 124, 126, 128 and termination time points 130, 132, 134and/or terminating events. In many situations, the device pair 106 maycontinue to communicate with each other over a period of time. Thesecommunications may take place in several communication periods 118, 120,122, rather than one continuous communication period 112.

Although FIGS. 1A-1C illustrated two devices 102, 104 communicating withone another, in some situations there may be more than two devicescommunicating with each other. For example, and as shown in FIG. 2A, twodevice networks 202, 204 may exist. Device A 206, device B 208, device C210 and device D 212 comprise a first device network 202. The seconddevice network 204 includes device E 214, device F 216, device G 218 anddevice H 220. FIG. 2A illustrates two separate device networks 202, 204,or, in other words, two distinct systems.

The first device network 202 includes one master and three slaves.Device A 206 serves as the master, while device B 208, device C 210 anddevice D 212 serve as slaves. The second device network 204 alsoincludes a master (device E 214) and three slaves (device F 216, deviceG 218, and device H 220). As shown, intrasystem communication 222 maytake place between the devices in the first device network 202 and inthe second device network 204.

One exemplary application of the embodiments herein may be with theBluetooth standard and the relevant personal area network technologyrelating to Bluetooth. The Bluetooth standard is described in theSpecification of the Bluetooth System, incorporated herein by reference.Depending on the particular communication system type, the applicationof the schedulers disclosed herein can be extended to what werepreviously considered internal system links. This may be particularlyapplicable to a Bluetooth system where a piconet is an independentsystem. In Bluetooth terms, the device networks 202, 204 may both bepiconets. When an interpiconet connection is made, the schedulersdisclosed herein may be applied to both the new connection and to theprevious intra-piconet connection of that device to its piconet master,if one previously existed.

Of course, it will be appreciated by those skilled in the art that theembodiments and inventive principles disclosed herein are not limited topersonal area network technology and/or to Bluetooth networks. Theinventive principles herein may be applied to various types ofcommunications systems that include electronic devices and/or computersthat communicate with each other.

Further to the example shown in FIGS. 2A-2D, there are generally threepossible ways of connecting the two networks 202, 204. As stated above,in FIGS. 2A-2D device A 206 and device E 214 serve as masters, while theother devices serve as slaves. Thus, master/slave relationships existbetween the masters and slaves of each device network 202, 204.

FIG. 2B illustrates an intersystem communication link 224 between deviceD 212 and device F 216. The scheduling apparatus and methods disclosedherein may be used with the intersystem communication link 224. Asshown, the links between device A 206 and device D 212 and betweendevice E 214 and device F 216 may also be treated as intersystem links224. Thus, the original connection between each slave and its master maynow be treated as an intersystem link because the slave devices may notbe available to the master at all times with the additional link.Communications between device A 206 and device D 212 and between deviceE 214 and device F 216 may be rescheduled because the capacity of theslaves (device D 212 and device F 216) is now being shared between twoconnections rather than just one connection.

FIG. 2C illustrates an intersystem communication link 224 between thetwo master devices 206, 214. FIG. 2D illustrates an intersystemcommunication link 224 between a master (device A 206) and a slave(device F 216). If the embodiments of FIGS. 2A-2D were implemented andused in a Bluetooth environment, the two systems 202, 204 and theintersystem communication 224 may be referred to as a scatternet. Asstated, the embodiments and inventive principles herein are not limitedto a Bluetooth environment but have broad application. The embodimentsherein provide solutions to the scheduling issues for devices that wishto have an arbitrary number of connections. Further, the embodimentsshown herein allow arbitrary topologies of devices to communicateeffectively when the connections are treated as intersystem connections.

FIG. 3A illustrates a simple system topology consisting of a device(electronic device B 302) that communicates with two other devices(device A 304 and device C 306). Electronic device A 304 and device B302 make up a device pair 308. Similarly, device B 302 and device C 306make up a device-pair 310.

For each pair 308, 310 of communicating devices, there is a schedule forcommunication indicating the initiation time points as shown in FIG. 3B.Communication periods 314, 316, 318 between device B 302 and device A304 are started through communication A-B initiation time points 320,322, 324. The initiation time points 320, 322, 324 start a communicationperiod 314, 316, 318 for the corresponding pair 308 of devices 304, 302.Communication periods 326, 328, 330 between device B 302 and device C306 are started through communication B-C initiation time points 332,334, 336. These initiation time points 332, 334, 336 start communicationperiods 326, 328, 330 for the B-C pair 310 of devices 302, 306. Asillustrated, each initiation time point becomes the terminating eventfor the preceding communication period. The end of the communicationperiod is signaled to the other device when another initiation timepoint occurs that conflicts with the current active communicationperiod. For example, initiation time point 320 starts a communicationperiod 314 between device A 304 and device B 302. This period 314continues until an initiation time point 332 occurs to signal thebeginning of a communication period 326 between device B 302 and deviceC 306. FIG. 3B illustrates the typical operation for the embodimentshown in FIG. 3A.

FIG. 4 illustrates a device network topology generalization. Acommunication link 402 exists between device A 404 and device B 406.Multiple devices X₁ to X_(n) are in electronic communication with deviceA 404. Similarly, multiple devices Y₁ to Y_(m) are in electroniccommunication with device B 406. The performance of the system providesfair distribution of capacity. This performance may be generalized inthe case where all links are fully utilized. The relationship is givenby the equation below for the generalized system that is diagrammed inFIG. 4. The capacity available to link A-B 402 is inversely proportionalto the total number of other intersystem links that both device A 404and device B 406 participate in. The equation below does not take intoconsideration the overhead due to switching between connections or othersignaling overhead needed for system operation. The Cap_(A-B) numberindicates the relative capacity available to a connection. It shows therelative amount of time that is utilized for communication between thedevice pair. This relation is applicable to a system where the densityof time points is equal for all intersystem links and each link has arandom distribution with respect to the others.${Cap}_{A - B} = \frac{1}{1 + n + m}$

FIG. 5 is block diagram illustrating the major hardware componentstypically utilized in an electronic/embedded device 500. An electronicdevice 500 typically includes a processor 502 in electroniccommunication with input components or devices 504 and/or outputcomponents or devices 506. The processor 502 is operably connected toinput 504 and/or output devices 506 capable of electronic communicationwith the processor 502, or, in other words, to devices capable of inputand/or output in the form of an electrical signal. Embodiments ofdevices 500 may include the inputs 504, outputs 506 and the processor502 within the same physical structure or in separate housings orstructures.

The electronic device 500 may also include memory 508. The memory 508may be a separate component from the processor 502, or it may beon-board memory 508 included in the same part as the processor 502. Forexample, microcontrollers often include a certain amount of on-boardmemory.

The processor 502 is also in electronic communication with acommunication module 510. The communication module 510 may be used forcommunications with other devices. Thus, the communication modules 510of the various devices may be designed to communicate with each other tosend signals or messages between the electronic devices 500.

The electronic device 500 may also include other communication ports512. In addition, other components 514 may also be included in theelectronic device 500.

Of course, those skilled in the art will appreciate the many kinds ofdifferent devices that may be used with embodiments herein. Accordingly,the block diagram of FIG. 5 is only meant to illustrate typicalcomponents of an embedded device 102, 500 and is not meant to limit thescope of embodiments disclosed herein.

FIG. 6 is a block diagram illustrating software modules that may be usedwith the electronic device 600. An embedded application 602 may be usedto operate the electronic device 600. The embedded application 602 mayinclude the functionality needed for operation of the electronic device600. An input/output module 604 may be used for receiving data from theinput(s) 504 and for sending data to the output(s) 506. Depending on thetype of electronic device 600, the particular functionality of theinput/output module 604 may vary.

A device communications module 606 may be included with functionality tohandle incoming and outgoing messages. For example, the devicecommunications module 606 may include the instructions necessary to sendand receive communications using the communications module 510. Thedevice communications module 606 may send or transmit outbound data 608and may receive inbound data 610.

The electronic device 600 typically includes software to accomplishvarious tasks including communications, input/output and the monitoringor controlling of the device 600. The device communications module 606represents the computer program routines or instructions that handle thecommunications through the communications module 510 or through thecommunications port(s) 512. The input/output module 604 represents thecomputer program routines or instructions that handle the input to thedevice 600 and the output from the device 600. For example, if therewere buttons (not shown) on the device 600, the input/output module 604includes the code necessary to process the inputs from the buttons (notshown). The application 602 controls the device 600 and acts as the mainprogram to carry out tasks of the device 600. Those skilled in the artwill appreciate that the software blocks are only examples and theconfiguration of blocks shown are not necessary to practice the presentembodiments. As explained earlier, many different types of devices 102,500, 600 are available and can be used with embodiments herein. Thesedevices usually already have the necessary software loaded to run thedevice 600. Embodiments herein can be used with almost all electronicdevices 102, 500, 600 that are capable of electronic communications andhave some processing capability.

The device may also include a pseudorandom scheduler 612 and a dynamicallocation scheduler 614. Both the pseudorandom scheduler 612 and thedynamic allocation scheduler 614 will be discussed below. As will bediscussed, the dynamic scheduler 614 may include a fair allocationcomponent 616 and an opportunistic allocation component 618.

An event queue 620 may also be included. The event queue 620 includesone or more queue items 622. Each queue item 622 may correspond to aparticular communication channel. Each queue item 622 may includecommunication time points 624, a channel identifier 626, data pending628, as well as other information, such as state information 630, statusinformation 632, and other information 634. The data that may be storedin the event queue 620 will be more fully discussed below.

A method is disclosed and provided herein to dynamically allocatecapacity between intersystem connections in the case where the scheduledallocation is not used by a device pair. A decentralized algorithm isused to distribute this capacity to the intersystem links where trafficis available. The unused capacity is allocated first on a fair basis andthen the capacity may be opportunistically allocated where communicationis possible. The algorithm attempts to maximize the utilization ofcommunication capacity for each device.

The principle employed to implement fair allocation is to effectivelyremove an intersystem connection from a device when there is no trafficwithout actually disconnecting. This causes the inherent fairness of thepseudo random scheduler 612 to reallocate the unused capacity to linksthat have traffic. In the embodiments herein, two mechanisms are used toachieve fair reallocation of unused capacity: initiation time pointreduction and extension of previous communication period.

In the initiation time point reduction method, a device monitors itsinternal event queue 620 and traffic on the link. If there is notraffic, the schedule is modified by removal of initiation time points.The schedule is modified so that there is only a fraction of theoriginal time points remaining. For example, in one possibleimplementation initiation time points may be removed so that only everyfourth of the original time points are used. This effectively removesthe connection to a device for a short intervals and allows its capacityto be used by other intersystem links. A negotiation process between adevice pair is used to modify the schedule and remove time points.

In the method where previous communication periods are extended, adevice will re-establish communication with the device that itpreviously communicated with when the current communication period isterminated early (i.e., terminations that occur before the nextinitiation time point). In this way it extends the previouscommunication period and effectively removes the device that has notfully used its scheduled capacity.

In principle, opportunistic allocation attempts to maximize the numberof parallel communication transfers. To achieve opportunisticallocation, additional processes are performed. In this process a device102 monitors the traffic pending for each link and the likelihood that adevice is available to establish communication. This information may bederived from the signaling that occurred when the previous communicationperiod was terminated for each of its intersystem links. The device 102may then attempt to establish communication with another device thatboth has data pending to transfer and is likely to be available. If morethat one device meets the criteria, the last one communicated with maybe selected. These rules improve the likelihood that both devices willattempt to establish a connection with each other.

Some applications have very rigid communication requirements that maynot be met with the pseudo random intersystem scheduler 612. Theserequirements are typically expressed in terms of fixed data bit rate andmaximum latency. Furthermore, the application will typically negotiatethe capability needed when establishing a channel for the service. Theservice will only be provided if sufficient capacity is available.

To accommodate more rigid requirements, a method to support resourcereserved channels (RRC) is provided. The resource reserved channel typemay be implemented as scheduled communication with a fixed period andduty cycle. Traffic for a resource reserved channel has higher prioritythan the pseudo random scheduled (PRS) channel so that it replaces thePRS traffic when a schedule conflict occurs. The PRS schedule ismodified to accommodate any RRC traffic. In current design, resourcereserved channels are negotiated such that they do not conflict witheach other.

Because of the periodic characteristic of the resource reserved channel,in many cases it will use a fixed capacity of the communication link.Because of the periodic characteristic, the capacity taken from the PRStraffic is randomly distributed among all links. As a result, theintersystem traffic that is scheduled by the PRS method is still fairlyallocated between intersystem connections although reduced by the RRC.

FIG. 7 illustrates an embodiment of a state machine for the scheduler ofa device 102. Each device 102 may implement this state machine toimplement a scheduler and to support other related functions. The systemdescription as it relates to the state machine may apply to aMAC/baseband entity responsible for managing the intersystem traffic forthe device 102. The information is equally applicable to both devices ofthe device pair unless otherwise stated. The protocol is based largelyon master/slave access mechanisms. The Bluetooth standards usemaster/slave relationships. For clarity and to illustrate an example ofhow the state machine may be used, the protocol is described inmaster/slave and sometimes Bluetooth terminology. Of course, it will beappreciated by those skilled in the art that the inventive principlesand embodiments herein may be applied to a wide range of electronicdevices 102 configured for electronic communications with other devices.

The idle state 702 is illustrated in FIG. 7. In the idle state 702,there is no PRS intersystem traffic. The device 102 is free tocommunicate with other devices in its system or network. The device 102may be designed to avoid communication that may extend into a PRSscheduled intersystem communication period. For a Bluetooth system, thiscan occur if a long packet is received that extends past a scheduledtime point.

The data state 704 is also illustrated in FIG. 7. In the data state 704,data is exchanged between intersystem devices. Communication continuesuntil a termination event occurs.

FIG. 7 also illustrates the negotiate schedule state 706. This state 706is used to modify the schedule. Either device may initiate this process706 or state 706. This state 706 is effectively a sub-state of the datastate 704 because an active communication period is needed to supportthe exchange of messages needed for the negotiation of schedule.

The re-establish state 708 is also illustrated in FIG. 7. There-establish state 708 implements a procedure for establishingcommunication during periods when there is no scheduled communication.This mechanism is used to distribute unused capacity to intersystemchannels that have data available for exchange.

FIG. 7 also illustrates events that may cause a transition from onestate to another or that may cause the device 102 to stay in the samestate. The intersystem schedule manager (not shown) maintains a list ofcommunication events for each intersystem channel in the event queue620. The event list will consist of an ordered list of scheduled timepoints 624 and corresponding channel identifiers 626. The scheduledevent occurs when the current time matches the scheduled time. When aninitiation time point occurs the device 102 will enter the data state704 and begin communication with the corresponding device. If the devicewas currently active with another communication channel it will performthe forced termination process on that channel before entering the datastate 704.

There are a number of different types of termination events that mayoccur. A forced termination occurs when there is a data exchange pendingbut one of the devices wishes to terminate the current communicationperiod. A device may wish to do this because of another scheduledintersystem communication (or an interpiconet communication in aBluetooth network) or for other reasons. The device terminates thecommunication period by asserting an indication of this event in amessage to the other device.

Another type of termination event is a scheduled termination. If thenegotiate schedule process 706 or state 706 was successfully completed,a termination time point was agreed upon for the current communicationperiod. A scheduled termination event occurs when this time pointoccurs.

A data depleted event is another type of termination event. This eventoccurs when all the available data has been transferred by both devices.This is signaled to the other device by a message indicating this event.A master device signals to the other device that it has no data totransmit by transmitting a Poll Packet. The slave indicates that it hasno data by transmission of a null packet. Thus, the data depletedtermination event occurs when both devices indicate that they have nodata to transfer.

Another type of termination event is a non-responsive termination event.A non-responsive termination event occurs when communication isscheduled but does not happen. A device may wait for communication for afixed period. If no data is received, the communication period may beterminated. If the device is a master, the non-responsive terminationevent occurs when it does not receive a response to any packetstransmitted to the slave device. If the device is a slave, thenon-responsive termination event occurs when it does not receive anypackets from the master. If the embodiment is being used with aBluetooth network, this situation may occur when there is a scatternetscheduling violation. It can also occur when a device has a higherpriority activity and cannot meet its agreed schedule. This will occurtypically for processes that have indeterminate duration (e.g., pageresponse, inquiry response).

Other types of events are also shown in FIG. 7 and further illustrateother events that may cause a change in state. A negotiate request eventis used by a device to initiate a negotiatie schedule process 706. Thisoccurs during the active communication period between the two devices.

The pending data event or status is an indication of the compositestatus of all the intersystem links as seen by a device. If any of thelinks were left in a state where data is remaining to be transferredthis indicator may be true. The state is known from the way in which acommunication period is terminated. For a link where the data depletedevent occurs this indicator may be false. For a link where a forcedtermination or a non-responsive termination occurs this indicator istrue.

The no pending data event or status is also an indication of thecomposite status of all the intersystem links as seen by a device. Thisindicates that none of a device's intersystem links have data pending.

The communication re-established event is also illustrated in FIG. 7.This event occurs when a poll response sequence has been completedvalidating that a communication channel has been established. Thefailure to re-establish event indicates that the device was not able toestablish communication in the re-establishment process 708.

As stated above, the idle state 702 is entered whenever there is noactive PRS intersystem communication. The amount of time spent in theidle state 702 is dependent on intersystem traffic load and on anymodification made to the pseudo randomly determined interpiconet (moregenerally intersystem) schedule. A device may modify the intersystemschedule to free time for the idle state 702 if needed for in-systemlinks or other activities. The idle state 702 may imply that the deviceis idle with respect to PRS intersystem traffic, but the device may beactive with other in-system communication activities.

While a device is in the idle state 702, it typically monitors theintersystem schedule and changes states when defined by the schedule.All other communication activities should be scheduled so that they willnot conflict with the intersystem schedule.

Referring to the data state 704 as shown in FIG. 7, intersystemcommunication starts when a scheduled initiation event occurs or whenthe re-establishment procedure 708 has been successful. The scheduledinitiation event is typically a time point defined by the pseudo-randomscheduler or may be another initiation time point that was previouslynegotiated between the devices. A communication period consists of theexchange of data between a device pair until a termination event.

In the data state 704 the master transmits packets to the slave. Datapackets are sent if available, otherwise poll packets are sent. This maybe done until a termination event occurs. The slave may listen for themaster transmitted packets. If packets from the master are received theslave transmits data packets if available and null packets otherwise.

A device detects a non-responsive condition by monitoring communicationactivity. If there is no communication for a non-responsive timeoutperiod slots, the device may terminate communication. For the masterdevice, it may transmit packets continuously to the slave device untilthe non-responsive timeout period expires. For the slave device, it maylisten continuously for packets from the master. If the slave has notreceived any packets for the non-responsive timeout period, it mayterminate the connection.

A device may terminate an active communication period at any time.Typically, a device will terminate the communication because it needs toperform another scheduled event. For example, the device may need to beavailable for an initiation time point for another link, it may need tocommunicate with a slave on an in-system link, etc.

A forced termination may be signaled by a device through a variety ofways. Depending upon the types of devices, systems, protocols, etc.,that are being used, different techniques may be implemented by a deviceto signal a forced termination. Generally, a device may send a forcedtermination message to other devices to communicate a forcedtermination. Those skilled in the art will appreciate the many differentways in which this message may be communicated. For example, in aBluetooth system, the forced termination may be signaled by a devicewith the flow bit of the packet header. The flow bit is normally enabled(FLOW=1) during the exchange of data. The device may clear it (FLOW=0)to force the termination of the current communication period.

A forced termination may also be preceded by a negotiate scheduleprocess 706. If used, it may indicate that the device that initiated thenew schedule is not available until the new negotiated time. This mayimply that this device is not available on this link for anyre-establishment. The negotiate schedule state 706 or process 706 may beused by the device that is terminating the active communication and isaware that it will be busy in the near future. If the forced terminationis not used, it may imply that the device is likely to be free forre-establishment of this link.

A data depleted termination occurs when both devices have no data toexchange. This happens when both devices empty their data queues.Similar to a forced termination, a data depleted termination may besignaled by a device through a variety of ways depending upon the typesof devices, systems, protocols, etc., that are being used. Generally, adevice may send a data depleted termination message to other devices tocommunicate a data depleted termination.

Those skilled in the art will appreciate the many different ways inwhich the data depleted termination message may be communicated. Forexample, in a Bluetooth system, this event may be signaled when theslave transmits a Null packet and the master transmits a Poll or Nullpacket. The termination slot is determined based on the last device tosignal that is has no data to transmit. The sequence Poll-Null-Poll withthe ACKN=0 may be used when the master is the last to run out of data.The last slot used is the Poll packet sent by the master. The sequenceNull-Poll-Null with ACKN=0 may be used when the slave is the last deviceto run out of data. In this case the Null packet from the slave is thelast slot to be used.

The schedule termination may occur if a negotiate schedule process 706was completed during the current active communication period. As part ofthis process, the beginning of the hold period (hold instant) wasnegotiated. The hold instant defines the last slave slot during thiscommunication period.

As stated above, the negotiate schedule state 706 or process 706 is usedto modify the schedule. A device may choose to modify the schedule forany number of reasons (e.g. conflict avoidance, etc). The devicemodifies its schedule to avoid wasting bandwidth by informing the otherdevice that it cannot meet the obligation of current schedule. A newschedule is then negotiated that is acceptable to both devices.

The negotiate schedule state 706 or process 706 may be used in severalsituations. The negotiate schedule state 706 may be used when there areinitiation time point event conflicts. In this situation, a device maylook ahead at the next time point for the current active communicationlink, if the next time point conflicts with a time point for anotherintersystem link and the other link has a higher priority, the negotiateschedule process 706 may be used to negotiate a new time point.

The negotiate schedule state 706 may be used when there is acommunication termination with no opportunity for re-establishment. Thismay happen if the communication period is going to be terminated by thelocal device and the link has pending traffic. The local device may lookahead at its predicted availability. If the device is expected to bebusy, it may use this procedure to indicate that it is not available byasserting the initiation time point. This information is used by there-establishment process 708 of the peer device in its selection ofcommunication links.

The negotiate schedule state 706 may be used when other events occur.For example, if the communication capability of the device is needed forother purposes, the device may make itself available by negotiatinginactive periods in the intersystem schedule. This may be done for eachintersystem link.

The negotiate schedule state 706 or process 706 may be initiated by thedevice that wishes to modify the current schedule. Different techniquesmay be used by a device to initiate a negotiate schedule process.Generally, a device may send a negotiate schedule initiation message toother devices to initiate a negotiate schedule process 706. Thoseskilled in the art will appreciate the many different ways in which thismessage may be communicated. For example, in a Bluetooth system, thestate may begin by transmission of an LMP_hold_req message where thehold instant parameter is set to equal the last slot of thecommunication period as determined by the initiation time point for anyother connections. The hold time parameter may be set to correspond tothe proposed next initiation time point for the connection. Thereceiving device may compare the requested hold instant to the next timepoint event that it has in its scheduled and accept it if it is less.Otherwise the device may request a new hold instant that corresponds toits next scheduled event. In current design, the embodiments areconfigured to attempt to agree on the shorter of the two periods. Thereceiving device may also inspect the hold time parameter and acceptthis parameter if it is able to meet that time. If not, it can proposethe next initiation time point for the channel. If both parameters areacceptable, it may send an LMP_Accepted. Otherwise it may transmit anLMP_hold_req with alternate requests. The receiving device may performsimilar checks and respond in the same way. After the negotiation iscomplete, the state may return to the Data state 704 and continueexchange of information until the termination event occurs.

The re-establishment state 708 attempts to opportunistically establishcommunication during periods that are not being used. The algorithm ispresently designed to initially fairly distribute unused capacitybetween devices when possible and to then opportunistically distributecommunication capacity where possible.

A device may enter into the re-establishment state 708 when the currentcommunication has been terminated and there is data pending on any ofits intersystem communication links. The device may attempt tore-establish communications on the previous active connection that hasdata transmission pending where the remote device has indicated that itmay be available. If the device is a master, this may consist of thetransmission of packets (Poll or data) until a response is received oranother initiation time point occurs. If a slave, it may listen untilanother initiation time point occurs. If a response is received thedevice may transition into the data state.

In the case where the device that terminated the communication periodsignaled that it will be busy, the free device may attempt to establishcommunication with another device that is likely to be available.

Each device may maintain an event queue 620 and state information 630for each intersystem communication channel. The event queue 620 mayconsist of an ordered list of time points. Each time point may begenerated from the pseudo random sequence for the correspondingconnection plus any negotiated modifications or additions. The devicemay combine the lists to determine which connections are scheduled atany point in time.

For each intersystem link status information 630 may be maintained. Thisinformation may be derived from the termination event plus any internaldata queue knowledge.

Each device may include link status information. The link statusinformation may include data pending 628 information, such as pending/nopending data. This may indicate if there is any pending transmission onthe link. This is set if there is any data pending transmission in thelocal queue or if the previous communication period was terminated witha data transmission pending event.

A device may also include a remote capacity indicator (not shown). Thismay indicate whether the remote device on a link is currently busy orfree. This indicator may be set to free if the previous communicationperiod was not terminated with a negotiate schedule event. Using thenegotiate schedule process implies that the remote device is busy untilthe new negotiated time.

Link schedule information (not shown) may also be stored on the device.Link schedule information may include pseudo random time points. Thesetime points may be automatically generated based on an algorithm thatdefines their position relative to the clock of the master device on thelink. These time points may also define the initiation of communication.

Scheduled time points may also be stored. These time points may becreated through a negotiation process between the two devices connectedby this link. These time points define the initiation of communication.A device may also store termination time points. These are time pointsthat define when communication should be terminated. They are created inthe negotiate schedule process 706.

Because initiation time points are typically generated pseudo randomly,conflicting time points may occur for devices that have two or moreintersystem links. The occurrence may be random with a rate dependent onthe density of time points. In embodiments disclosed herein, a devicedetects the conflicting time points and adjusts the schedule toeliminate them. The device may use the negotiate schedule state 706 orprocess 706 to move or skip conflicting time points when possible. Whenit is not possible to reschedule conflicting initiation time points, thedevice should select communication with the device with the longestinactive period over other devices. This assures a fair allocation ofbandwidth and minimizes inactive periods.

A pseudo random generator may be used to create the initiation timepoints that make up the schedule. Time points may be defined withreference to the clock of the master device of the device pair thatmake-up the intersystem connection. In current design, both devices areable to independently create the schedule and both have knowledge of theclock needed to utilize the schedule. Given that each schedule may beunique and random with respect to other intersystem schedules, a uniquebut shared piece of information may be used as input to the generator.For example, if the devices were part of a Bluetooth network, thisshared piece of information may be the Bluetooth device address(BD_ADDR) of the master and active member address (AM_ADDR) of theslave.

One characteristic of the generator is its density, which defines theaverage time between time points. Other temporal relations may also beimposed on the generation function to achieve particular operatingcharacteristics. Three possible methods and related characteristics aredescribed below. The following methods may be used but each has its ownunique system limitations and performance tradeoffs. Those skilled inthe art will appreciate that other methods may also be used withembodiments of devices and device software to effect scheduling ofcommunication periods.

FIG. 8A illustrates a predetermined synchronized method for generatingtime points. As shown, in the predetermined synchronized time methodtime points are generated by first breaking the schedule into fixedperiod intervals (A). The duration of the intervals corresponds to thedensity of time points desired. A single time point is placed within theinterval at a random location. Following is an equation that describedhow a time point is generated using this method.TP _(N) =A×N+Rand(0 . . . A)

In the foregoing equation, A defines the interval size, and N is theinterval number and index to the time point. The function Rand( )provides a random number in the range of 0 to A. A unique random numberis generated for each time point.

This predetermined synchronized method has the advantage that the rangeof communication period lengths can be influenced by the distribution ofthe time point positions. Different distributions of random numbers canbe used to control the statistical characteristics of the communicationperiod length. Typically a uniform distribution of random number wouldbe used. But, for example, to achieve a communication period durationmore narrowly distributed around the mean a normal distribution ofrandom numbers centered at A/2 may be used. This would reduce thevariation in communication period length but increase the probability ofcollisions when compared to a uniform distribution.

This method is primarily applicable to systems where the interval issynchronized between intersystem links. It has the advantage ofproviding a tighter bound on the maximum delay between communicationperiods and may better control the statistical distribution of thecommunication period duration.

FIG. 8B illustrates a predetermined asynchronized method for generatingtime points. As shown, in this method of generation time point positionsare determined by random number generation over an arbitrary long time.This period is typically many times greater than the density. Typically,this should be 10 to 100 times greater that the average period betweentime points. Time points are generated randomly with uniformdistribution in this period. The time points are then sorted intoascending order for usage by the scheduler.TP _(0 . . . M) =Rand(0 . . . A*N)TP _(0 . . . N) =Sort(TP _(0 . . . M))

In the foregoing equation, TP_(0 . . . N) is the ordered list of timepoints used by the scheduler. The Rand( ) function generates time pointsthat are uniformly distributed over the period defined by the density(A) and number of time points needed (N). The total duration that therandom numbers are uniformly generated in is determined by the productof the density (A) required and the number of time points (N).

The predetermined asynchronized method has the advantage that there isno synchronization needed between clocks of different intersystem links.Its primary disadvantage when compared to the predetermined synchronizedmethod is that the characteristics of the communication period are notbounded. The communication period length and time between communicationperiods is more variable.

FIG. 8C illustrates a real-time method for generating time points. Inthe real-time method, time points are generated relative to previoustime points. This is primarily applicable to the case where it isdesirable to generate the schedule in real-time although it can also beused to predetermine a schedule. To perform the real-time method, adevice may generate a random number with uniform distribution in therange between 0 and 2 times the density. This number is added to theprevious initiation time point to determine the next initiation timepoint. This information to transferred to the other device. This processis carried out by one of the devices in the device pair, typically themaster. This method is particularly applicable to Hold mode in theBluetooth System.

The intersystem scheduler allows Resource Reserved Channel (RRC) trafficto coexist with Pseudo Random Scheduled (PRS) intersystem traffic. Theembodiments described herein allow this coexistence while maintainingthe fair performance characteristics of the best effort channel (BEC)provided by the pseudo random scheduler. Two mechanisms are defined tomanage the coexistence of the RRC channel types on top of the BECchannel: the traffic overlay method and the dynamic schedulemodification method.

The traffic overlay method is used when the active period of theResource Reserved traffic is relatively short compared to the PRSaverage communication period. If the active period is less than thenon-responsive termination event timeout threshold, a device is allowedto provide this channel without modifying the intersystem schedule. Inthis case, the device will simply transmit the RRC traffic in place onthe PRS traffic. After completion it will return to the PRS scheduledtraffic. If the device is nearing the end of the communication period itwill terminate the communication early and then proceed with the RRCtraffic.

The schedule modification method is used when the active period of theRRC traffic is long relative to the average communication period lengthor if it is longer than the non-responsive termination event thresholdof the PRS scheduled traffic. In this case, the PRS schedule is modifiedto free time for this traffic. This occurs in the communication periodprior to the period for the RRC traffic.

To accommodate in-system data traffic a device must have time availableto service it. This free time corresponds to the idle state 702 in theintersystem state machine. A device may use the free time that naturallyoccurs in the intersystem scheduled traffic or choose to modify theintersystem schedule to make free time available. In the latter case thedevice can make free time in the intersystem traffic by re-negotiatingthe intersystem schedule. This is equivalent to the process that is usedto manage resource reserved channels. Typically this would be doneperiodically to meet requirements for in-system communication.

A device may also choose to treat an in-system link as if it is anintersystem link. In this case it may use a PRS schedule for thein-system link and get the same performance characteristics as anintersystem link. The method used may be dependent on the timingrequirements of the in-system communication.

FIGS. 9A and 9B illustrate a device network configuration and the uniquepseudo-random schedule generated for each connection. As shown in FIG.9A, the device network includes three masters 902, 904, 906 and oneslave 908. In a Bluetooth system, the configuration shown in FIG. 9Amakes up three piconets (one master for each piconet).

The communication periods diagram of FIG. 9B illustrates severalintervals. As shown, the density used enables an average of onecommunication period per interval. As discussed above, a communicationperiod starts with an initiation time point and it ends when aconflicting time point occurs or with a termination time point.

FIGS. 10A and 10B illustrate a device network configuration includingfour piconets. As shown in FIG. 9A, the device network includes threemasters 1002, 1004, 1006, one slave 1008, and one master/slave 1010. Thecommunication periods diagram of FIG. 10B illustrates a minimum capacityallocated to each connection. As discussed herein, dynamic allocationmay be used to recover unused capacity.

FIGS. 11A and 11B illustrate fair allocation of unused capacity by adevice network. In this example, there was no traffic between device A1102 and device D 1104. As a result, the original communication periodsfor the device A 1102-device D 1104 pair were unused capacity. For theexample of FIGS. 11A and 11B, also assume that full capacity was beingused between devices B 1106 and D 1104 and between devices C 1108 and D1104. In fair allocation, the unused capacity of the device A1102-device D 1104 pair is randomly used by either the device B1106-device D 1104 pair or by the device C 1108-device D 1104 pair. In aBluetooth system, this would effectively make device A 1102 appear to beabsent from the scatternet.

FIGS. 12A and 12B illustrate opportunistic and fair allocation of unusedcapacity by a device network. In this example, there was no trafficbetween device A 1202 and device D 1204. As a result, the originalcommunication periods for the device A 1202-device D 1204 pair wereunused capacity. For the example of FIGS. 12A and 12B, also assume thatfull capacity was being used between devices B 1206 and D 1204, betweendevices C 1208 and D 1204, and between devices E 1210 and C 1208. Withfair allocation, a terminating event caused by a device that is notactive causes the free device to remain on the same channel and toattempt reestablishment. With opportunistic allocation, a terminatingevent caused by an active busy channel causes the free device to switchto an alternate channel. Thus, opportunistic allocation allows moreparallel exchange of data. As shown in the communication periods diagramof FIG. 12B, the unused capacity of the device A 1202-D 1204 pair isfairly allocated and opportunistically allocated to other channels touse the capacity.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrative,and not restrictive. The scope of the invention is, therefore, indicatedby the appended claims, rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. A first electronic device adapted to communicate with a first devicenetwork and adapted to communicate with a second electronic device thatis part of a second device network, the device comprising: a processor;a communications module in electronic communication with the processorfor communications with other devices including the second electronicdevice and at least one device from the first device network; memory inelectronic communication with the processor for storing data; apseudo-random scheduler for providing pseudo-random time points defininga schedule for the first electronic device to communicate with the firstdevice network and with the second electronic device; a dynamicscheduler to dynamically modify the schedule to add additionalcommunication bandwidth to at least one communication channel; and anevent queue.
 2. The electronic device as defined in claim 1 wherein thedynamic scheduler implements a fair allocation method of dynamicallyallocating communication bandwidth.
 3. The electronic device as definedin claim 2 wherein the fair allocation method comprises extendingprevious communications periods.
 4. The electronic device as defined inclaim 2 wherein the fair allocation method comprises reducing the numberof initiation time points in the event queue.
 5. The electronic deviceas defined in claim 1 wherein the dynamic scheduler implements anopportunistic allocation method of dynamically allocating communicationbandwidth.
 6. The electronic device as defined in claim 5 wherein theopportunistic allocation method comprises evaluating traffic pending anddevice availability and modifying the schedule based on the evaluation.7. The electronic device as defined in claim 1 wherein the pseudo-randomscheduler implements a predetermined synchronized method for generatingtime points.
 8. The electronic device as defined in claim 1 wherein thepseudo-random scheduler implements a predetermined asynchronized methodfor generating time points.
 9. The electronic device as defined in claim1 wherein the pseudo-random scheduler implements a real-time method forgenerating time points.
 10. The electronic device as defined in claim 1wherein the event queue comprises a plurality of initiation time points,a plurality of channel identifications and a plurality of data pendingindicators.
 11. The electronic device as defined in claim 1 wherein theelectronic device further comprises a state machine for scheduling andcommunicating, the state machine comprising an idle state, a data state,a negotiate schedule state and a re-establish state.
 12. The electronicdevice as defined in claim 1 wherein the electronic device is configuredto become part of a piconet.
 13. The electronic device as defined inclaim 1 wherein the pseudo-random scheduler provides the time pointsdefining the schedule for the electronic device to communicate with afirst piconet and a second piconet.
 14. The electronic device as definedin claim 1 wherein the dynamic scheduler is configured to enter anegotiate schedule state to determine new time points and to then modifythe schedule using the new time points.
 15. (canceled)
 16. Theelectronic device as defined in claim 1 wherein the electronic device isconfigured to send a forced termination message to terminate acommunications period.
 17. The electronic device as defined in claim 1wherein the electronic device is configured to send a data depletedtermination message to terminate a communications period.
 18. Theelectronic device as defined in claim 1 wherein the electronic device isconfigured to generate termination time points to schedule terminationsof communications periods.
 19. The electronic device as defined in claim1 wherein the electronic device is configured to implement a trafficoverlay method to manage resource reserved traffic.
 20. The electronicdevice as defined in claim 1 wherein the electronic device is configuredto implement a dynamic schedule modification method to manage resourcereserved traffic.
 21. A computer-readable medium for carrying programdata, wherein the program data comprises executable instructions forimplementing a method comprised of the steps of: transmitting outbounddata from a first electronic device to a first device network; receivinginbound data by the first electronic device from the first devicenetwork; discovering a second electronic device of a second devicenetwork; providing pseudo-random time points defining a schedule for thefirst electronic device to communicate with the first device network andwith the second electronic device; storing the time points in an eventqueue; and dynamically modifying the schedule to add additionalcommunication bandwidth to at least one communication channel.
 22. Thecomputer-readable medium as defined in claim 21 wherein the step ofdynamically modifying implements a fair allocation method of dynamicallyallocating communication bandwidth.
 23. The computer-readable medium asdefined in claim 22 wherein the fair allocation method comprisesextending previous communications periods.
 24. The computer-readablemedium as defined in claim 22 wherein the fair allocation methodcomprises reducing the number of initiation time points in the eventqueue.
 25. The computer-readable medium as defined in claim 22 whereinthe step of dynamically modifying implements an opportunistic allocationmethod of dynamically allocating communication bandwidth.
 26. Thecomputer-readable medium as defined in claim 25 wherein theopportunistic allocation method comprises evaluating traffic pending anddevice availability and modifying the schedule based on the evaluation.27. The computer-readable medium as defined in claim 21 wherein theproviding pseudo-random time points step implements a predeterminedsynchronized method for generating time points.
 28. Thecomputer-readable medium as defined in claim 21 wherein the providingpseudo-random time points step implements a predetermined asynchronizedmethod for generating time points.
 29. The computer-readable medium asdefined in claim 21 wherein the providing pseudo-random time points stepimplements a real-time method for generating time points.
 30. Thecomputer-readable medium as defined in claim 21 wherein the event queuecomprises a plurality of initiation time points, a plurality of channelidentifications and a plurality of data pending indicators.
 31. Thecomputer-readable medium as defined in claim 21 wherein the methodfurther comprises implementing a state machine for scheduling andcommunicating, the state machine comprising an idle state, a data state,a negotiate schedule state and a re-establish state.
 32. Thecomputer-readable medium as defined in claim 21 wherein the first devicenetwork is a piconet.
 33. The computer-readable medium as defined inclaim 32 wherein the second device network is a piconet.
 34. Thecomputer-readable medium as defined in claim 21 wherein the methodfurther comprises entering a negotiate schedule state to determine newtime points and to then modify the schedule using the new time points.35. (canceled)
 36. The computer-readable medium as defined in claim 21wherein the method further comprises sending a forced terminationmessage to terminate a communications period.
 37. The computer-readablemedium as defined in claim 21 wherein the method further comprisessending a data depleted termination message to terminate acommunications period.
 38. The computer-readable medium as defined inclaim 21 wherein the method further comprises generating terminationtime points to schedule terminations of communications periods.
 39. Thecomputer-readable medium as defined in claim 21 wherein the methodfurther comprises using a traffic overlay method to manage resourcereserved traffic.
 40. The computer-readable medium as defined in claim21 wherein the method further comprises using a dynamic schedulemodification method to manage resource reserved traffic.
 41. A methodfor pseudo-randomly and dynamically scheduling communication periodsbetween electronic devices, the method comprising: transmitting outbounddata from a first electronic device to a first device network; receivinginbound data by the first electronic device from the first devicenetwork; discovering a second electronic device of a second devicenetwork; providing pseudo-random time points defining a schedule for thefirst electronic device to communicate with the first device network andwith the second electronic device; storing the time points in an eventqueue; and dynamically modifying the schedule to add additionalcommunication bandwidth to at least one communication channel.
 42. Themethod as defined in claim 41 wherein the step of dynamically modifyingimplements a fair allocation method of dynamically allocatingcommunication bandwidth.
 43. The method as defined in claim 42 whereinthe fair allocation method comprises extending previous communicationsperiods.
 44. The method as defined in claim 42 wherein the fairallocation method comprises reducing the number of initiation timepoints in the event queue.
 45. The method as defined in claim 42 whereinthe step of dynamically modifying further implements an opportunisticallocation method of dynamically allocating communication bandwidth. 46.The method as defined in claim 45 wherein the opportunistic allocationmethod comprises evaluating traffic pending and device availability andmodifying the schedule based on the evaluation.
 47. The method asdefined in claim 46 wherein the providing pseudo-random time points stepimplements a predetermined synchronized method for generating timepoints.
 48. The method as defined in claim 46 wherein the providingpseudo-random time points step implements a predetermined asynchronizedmethod for generating time points.
 49. The method as defined in claim 46wherein the providing pseudo-random time points step implements areal-time method for generating time points.
 50. The method as definedin claim 46 wherein the event queue comprises a plurality of initiationtime points, a plurality of channel identifications and a plurality ofdata pending indicators.
 51. The method as defined in claim 50 whereinthe method further comprises implementing a state machine for schedulingand communicating, the state machine comprising an idle state, a datastate, a negotiate schedule state and a re-establish state.
 52. Themethod as defined in claim 51 wherein the first device network is apiconet.
 53. The method as defined in claim 52 wherein the second devicenetwork is a piconet.
 54. The method as defined in claim 41 furthercomprising entering a negotiate schedule state to determine new timepoints and to then modify the schedule using the new time points. 55.(canceled)
 56. The method as defined in claim 41 further comprisingsending a forced termination message to terminate a communicationsperiod.
 57. The method as defined in claim 41 further comprising sendinga data depleted termination message to terminate a communicationsperiod.
 58. The method as defined in claim 41 further comprisinggenerating termination time points to schedule terminations ofcommunications periods.
 59. The method as defined in claim 41 furthercomprising using a traffic overlay method to manage resource reservedtraffic.
 60. The method as defined in claim 41 further comprising usinga dynamic schedule modification method to manage resource reservedtraffic.